home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Turnbull China Bikeride
/
Turnbull China Bikeride - Disc 2.iso
/
BARNET
/
ARMLINUX
/
MAIL
/
9712
/
000007_pb@nexus.co.uk _Mon Dec 1 14:01:24 1997.msg
< prev
next >
Wrap
Internet Message Format
|
1998-01-04
|
2KB
Return-Path: <pb@nexus.co.uk>
Received: from globe (nexusel.demon.co.uk [158.152.30.195])
by odie.barnet.ac.uk (8.8.6/8.8.6) with SMTP id OAA17670
for <willy@odie.barnet.ac.uk>; Mon, 1 Dec 1997 14:01:23 GMT
Received: from spring.nexus.co.uk [192.0.0.3] (exim)
by globe with smtp (Exim 1.73 #1)
id 0xcWPG-0002HR-00; Mon, 1 Dec 1997 14:01:02 +0000
Received: from spring.nexus.co.uk [127.0.0.1] (pb)
by spring.nexus.co.uk with esmtp (Exim 1.73 #2)
id 0xcWOh-00053i-00; Mon, 1 Dec 1997 14:00:27 +0000
X-Mailer: exmh version 2.0zeta 7/24/97
To: Matthew Wilcox <willy@odie.barnet.ac.uk>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: gcc
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 01 Dec 1997 14:00:27 +0000
From: Philip Blundell <pb@nexus.co.uk>
Message-Id: <E0xcWOh-00053i-00@spring.nexus.co.uk>
Status: RO
>/usr/local/arm-linuxaout/include/asm. This isn't explicitly stated -
>and I'm not sure that it's really necessary since the SWI numbers are
>unlikely to change - indeed, they can't without breaking every binary,
>and library, on the system.
Actually, that's not quite true. It's possible to replace the current
syscalls with new ones and retain the old numbers as compatibility wrappers.
In that case we'd want newly-compiled code to use the shiny new syscalls
rather than the old ones.
Now, if you _really_ want to live life on the edge, get the latest glibc 2.1
snapshot from ftp.kernel.org:/pub/linux/libs/glibc, compile that for
arm-linuxaout with your new gcc, and see if you can actually build some
working executables with it. Again, I'd like to know how you get on if
anybody tries this.
p.